Hide Secrets Manager from public API docs until GA - #1210
Merged
anup-deka merged 1 commit intoJul 31, 2026
Conversation
Comment out Secrets Manager paths so they are not published while the product is not generally available, keeping the operation files for easy restore. Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Jul 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/v2/security/secrets*) in the public OpenAPI root so they are not published to docs.digitalocean.comresources/security/so they can be restored by uncommentingCustomers are discovering Secrets Manager via public docs and receiving 403s because the product is not generally available.
Test plan
make lintpasses locallyMade with Cursor